Release notes
TIP: Looking for release notes for all Axiom products, including current and previous versions? Click here.
NOTE: You can download a PDF version of the release notes here.
New features in 2020.1
See What's new.
IMPORTANT: See the Technical Considerations section below for important information regarding the CostResultsUsage table and account number length in regards to invalid reclass and overhead allocation rules.
What to know before upgrading
IMPORTANT: You must apply the Axiom Software 2020.1 upgrade before applying any 2020.1 Axiom product upgrades. Axiom Software upgrades are backwards compatible so you can upgrade different products at different times, but you must upgrade to the Axiom Software 2020.1 before the first product upgrade. Refer to the Axiom Software 2020.1 Release Notes and Axiom Healthcare Suite 2020.1 Release Notes for considerations before upgrading. Apply this update ONLY if you have already applied the release and completed all the manual setup steps from the corresponding release notes.
When upgrading to the 2020.1 version of Axiom Cost Accounting, keep in mind the following:
- This product upgrade contains updated templates, calculation methods, driver files, and remediated defects.
- KHA delivered reports may be removed or replaced. Any report that you saved under a different name or created new will remain untouched. Replaced reports are available in Document History, if needed.
- Any KHA delivered report that was moved to a new location by the client will automatically move back to its original location.
- KHA product templates and calculation method libraries will be replaced.
-
Process definitions will not be replaced. Process Manager will not currently work with the new system tables and web-based pages and utilities. Consequently, please plan on reviewing and potentially revising any Cost Accounting Process Definitions depending on the scope and what tasks have been created and are in use.
-
Security roles and sub-systems will be reset to their configured settings for the Axiom defined roles. All security exceptions you may have made at the individual user level will remain intact.
-
Specific items configured as part of your company or organization's implementation such as imports, exports, driver files, and process management files, will remain as is. Any required modifications to these areas are covered in the release notes, if required. For example, Process Manager defined processes for Cost Accounting will need to be modified by Client Success and has limitations with accessing web-based tasks.
Preparing for and scheduling upgrades
Summary of the upgrade process:
-
Review product release notes – Review this document to familiarize yourself with the new features and functionality.
-
Schedule an installation date – Submit a request to your organization's Axiom Master System User (MSU) to contact support@kaufmanhall.com to schedule an installation date and time with at least three days of advance notice. The request should include the following information:
-
Desired Axiom Software platform version.
-
Desired Axiom for Healthcare product and version.
-
Indicate whether to first refresh the Axiom test sandbox with a copy of the production instance of Axiom and apply update(s) to it. If so, provide the soonest that Kaufman Hall can do this.
-
Propose an approximate two-hour downtime window when Kaufman Hall can apply update(s) to the production instance of Axiom during regular business hours, Monday through Friday 7 AM to 7 PM Central (except holidays recognized by Kaufman Hall).
-
-
Complete manual configuration updates – After installing the upgrade, review any manual setup steps needed to enable features for this version.
Getting help and training
Kaufman Hall provides world-class resources at your fingertips directly within the Axiom Software system. Axiom Help provides topics, knowledge base articles, documents, webinar/training announcements, and videos to guide you through managing your system. To access these resources, do any of the following:
-
Online help - From the Main or Admin ribbon tab, click Online Help, and then select the product. Axiom Help opens in a new browser window. The online help will only open for products you are licensed to use.
-
Contextual help - Form/web-enabled features include contextual help directly within the user interface. This information provides a quick summary and/or instructions specifically related to the screen you are using. You can access this information by clicking the question mark in the upper right corner of the screen. For more detailed information, open Axiom Help by clicking Open Help at the top of the contextual help dialog.
Escalating to Axiom Support
As always, we appreciate your commitment to Kaufman Hall. If you have any questions about your upgrade, please contact us by logging into Axiom, navigating to the online help for your product, and clicking the Support at the top of the home page.
2020.1 - Known issues resolved
The following table lists the resolutions for issues addressed in 2020.1, released on April 30th, 2020:
| Issue | Description |
|---|---|
| WebUI: Dimension Default Value Add Row bucketlist Special Characters [TFS 43180] |
Issue: The system displays an error message when a user saves dimension changes that include special characters. Resolution: Corrected by adding the Dimension key validation to the Dimension web page. This validates both the max character length and the new 'bad' special characters set. |
2020.1.1 - Known issues resolved
No client facing issues were addressed in 2020.1.1, released on May 12th, 2020.
2020.1.2 - Known issues resolved
The following table lists the resolutions for issues addressed in 2020.1.2, released on June 8th, 2020:
| Issue | Description |
|---|---|
| PFB-08580 - Sum Cost Detail Category to Encounter Detail Category [TFS 49482] |
Issue: The Cost Assignment import utility, Sum Cost Detail Category to Encounter Detail Category in 2019.4 does not fully update the EDCC table from CDCC for encounters discharged based on the transaction start and end ServiceYRMO when run for a current or prior period (CostSet). Resolution: Corrected by removing additional constraints in the query that summarizes the Cost Detail Category Calculation (CDCC) table to the Encounter Detail Category Calculation (EDCC) table. |
| PFB-08924 - ReclassDefinition and AllocationDefinition table columns error during 2020.1 product update [TFS 49533] |
Issue: The following error messages displayed when updating Cost Accounting 2019.3 to 2020.1:
Resolution: Corrected by updating the string from 500 to 4000 in filter fields in the AllocationDefinition and ReclassDefinition tables. |
2020.1.3 - Known issues resolved
No client facing issues were addressed in 2020.1.3, released on July 20th, 2020.
2020.1.4 - Known issues resolved
No client facing issues were addressed in 2020.1.4, released on August 17th, 2020.
2020.1.5 - Known issues resolved
No client facing issues were addressed in 2020.1.5, released on September 25th, 2020.
2020.1.6 - Known issues resolved
The following table lists the resolutions for issues addressed in 2020.1.7, released on November 9th, 2020:
| Issue | Description |
|---|---|
| RCC costing calc not including dept.costmaps [TFS 62220] |
Issue: The RCC costing calculator did not include a join using dept.costmap, which caused the system to omit offset CGL records from being created. This occurred when a cost map included usage (CostItemUsage) and method definitions, but the children department was used as the base expense on the CGL table without including the parent department. This could cause incorrect cost results for the downstream calculator RCU, which uses the results from RCC (both CGL records and cost results) to allocate the remaining expense dollars, configured for RCU. Resolution: Corrected by updating the RCC post job to account for cost map mappings. |
2020.1.7 - Known issues resolved
The following table lists the resolutions for issues addressed in 2020.1.7, released on December 7th, 2020:
| Issue | Description |
|---|---|
| Sum CDCC to EDCC job fails in large volume systems [TFS 61745] |
Issue: When importing data using the Sum Cost Detail Category to Encounter Detail Category.axi ETL, the system displays an error message that the import failed. Resolution: Corrected by updating the ETL to load into the CDCC using smaller batches of data. |
2020.1.8 - Known issues resolved
The following table lists the resolutions for issues addressed in 2020.1.8, released on February 15th, 2021:
| Issue | Description |
|---|---|
| 2020.1 CostDetailBase & CostDetailTotalCost allows duplicate transactionids [TFS 80060] |
Issue: Running an import that saves to the CostDetailBase and updates an existing servicedate may cause a duplicate transaction to be created. Resolution: Corrected by adding a new transformation to the beginning of the CostDetailStaging to CostDetail import that updates the serviceyrmo for any transactionid where the imported serviceyrmo is different than the one stored in the database. IMPORTANT: See the Add new transformation step to customized version of Import CostDetail from Staging.axi for instructions on configuration steps you may need to complete related to this resolved defect. |
Add new transformation step to customized version of Import CostDetail from Staging.axi
A new transformation step has been added to \Axiom\Imports Library\Costing\02 Internal Data\Import CostDetail from Staging.axi that prevents duplicate record creation in the CostDetailBase table. Many clients use a customized version of this import, so you may need to add this new transformation step to your version.
The best way to do this is to identify the import that your organization uses to import cost detail records and, if the version you are using does not point to \Axiom\Imports Library\Costing\02 Internal Data\Import CostDetail from Staging.axi, then you will need to copy transfromation step 1 from \Axiom\Imports Library\Costing\02 Internal Data\Import CostDetail from Staging.axi to your version.
CostResultsUsage table
In Axiom Cost Accounting 2019.4 Patch 1, it was discovered that the CostResultsUsage table was no longer referred to by the original reports it was meant to support. To improve cost processing performance, we deprecated the table, and as a result, the system no longer writes data to the table.
IMPORTANT: If your organization uses exports or reports that use data points from this table, you will need modify the exports/reports to point them to point them to tables post 2019.4 upgrade.
Account number lengths and invalid reclass/overhead allocation rules
Post 2019.1, the system identifies reclass and overhead allocation rules as invalid if the associated account numbers are less than 13 digits. Review the following process diagram to determine the appropriate steps to resolve this issue.
Click image to view full size
